System and method for implementing a rtp-signaled terminal hand over

ABSTRACT

An improved system and method for implementing communications hand over in a simple manner. RTP is used to signal to other terminals that an IP address has been changed for a particular. The receiving communications application notices from the RTP data flow that the other party in a communications session has changed its IP address. Based on this information, the communications application adjusts the communications session without having to perform any session signaling.

FIELD OF THE INVENTION

The present invention relates generally to the use of the Real-Time Transport Protocol (RTP). More particularly, the present invention relates to the use of the RTP protocol in implementing IP communications session hand over functionality without requiring support from a network.

BACKGROUND OF THE INVENTION

This section is intended to provide a background or context to the invention that is recited in the claims. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and claims in this application and is not admitted to be prior art by inclusion in this section.

Mobile terminals require hand over functionality with communications services. For example, when a user moves and/or changes an access network interface, it is important that his or her call not be interrupted during the process. Some access networks implement mobility in layer 2 (e.g. wireless code division multiple access (WCDMA) and Global System for Mobile Communication (GSM)) or by using mobile IP (e.g. WiMAX or Internet-High-Speed Downlink Packet Access (I-HSDPA)). However, there are currently many types of IP networks that do not offer mobility by any mechanism, for example in the case of Wireless Local Area Network (WLAN) hotspots. Additionally, the use of Mobile IP requires the use of a home agent, and the home agent affects the traffic flows (e.g., traffic travels via the home agent).

Multi-radio terminals are becoming increasingly common as the technology surrounding these devices continues to improve at a substantial rate. As a result, a mobile terminal is now more likely than in the past to have many different radio interfaces that it can utilize for communications purposes. For example, a single mobile terminal may be capable of supporting GSM, WCDMA and WLAN. In future products, WiMAX and HSDPA are also expected to be incorporated, resulting in still more interfaces for a terminal.

Traditionally, hand over functionality has been integrated into the mobile networks. However, with several different technologies currently emerging, the hand over implementation is becoming more and more complex (e.g. hand over from GSM to WLAN). With IP networks becoming common, mobility is often being implemented by using mobile IP. There is also currently ongoing work to implement a voice call continuity service that focuses on the hand over from circuit switched voice system to packet voice systems.

Currently, a problem occurs whenever IP end points move and utilize the nomadic mobility provided by IP networks via, for example, the Dynamic Host Configuration Protocol (DHCP). When a terminal starts to use a new interface, or when the terminal moves, e.g. from one hotspot to another, it is common for the applications IP address and terminal routing table to change, as the IP address is tied to an interface. This causes current communications applications to loose connectivity. In IP-based networking, the applications are unaware of the access technologies that are used, and terminal applications usually only send packets to some destination IP address that the terminal routes according to the terminal's routing table (the routing table chooses the interface to be used).

In most instances, the routing table utilizes a default route that points to a connected interface that has the highest priority. It is possible that, during a communications session, the terminal may attach to a higher priority interface (e.g. WLAN) and the default route changes, causing an ongoing communications session to drop. It is also possible that the terminal may move out of coverage for a certain interface (e.g., out of a WLAN hot spot) so that the default route starts pointing to some other interface (e.g., WCDMA). Whenever the used interface changes, the IP address also changes. Otherwise, returning packets may experience black hole routing, as the previous interface may no longer be reachable from the Internet.

SUMMARY OF THE INVENTION

The present invention provides an improved system and method for implementing communications hand over in a simple manner. In various embodiments of the present invention, RTP is used to signal other users that an IP address has been changed. The receiving communications application notices from the RTP data flow that the other party in a communications session has changed its IP address. Based on this information, the communications application adjusts the communications session without having to perform any session signaling.

The system and method of the various embodiments of the present invention is suitable with all different signaling protocols, e.g., Session Initiation Protocol (SIP), H.323, Media Gateway Control Protocol (MGCP), Extensible Messaging and Presence Protocol (XMPP), etc. Additionally, no equipment or control is needed in the network to assist in the “hand over” from one interface to another. Instead, the various embodiments can be implemented purely within the terminal applications. Additionally, the terminal can make decisions about which interfaces to use, prefer and prioritize. Furthermore, no additional signaling traffic is required in the communications control layer, and any party to a communications session can perform the hand over. Still further, the various embodiments of the present invention are not tied to any specific access technology. Instead, the various embodiments can be used within the same access in the event that the IP address is changed (e.g. from one WLAN hotspot to another WLAN hotspot), or the embodiments can be used when moving from one access network to another (e.g. from a WCDMA network to a WLAN network). Lastly, the accesses that are used by a terminal can come from different operators.

These and other advantages and features of the invention, together with the organization and manner of operation thereof, will become apparent from the following detailed description when taken in conjunction with the accompanying drawings, wherein like elements have like numerals throughout the several drawings described below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a depiction of the process by which a changed interface/IP address is signaled using RTP packets in accordance with one embodiment of the present invention;

FIG. 2 is a perspective view of an electronic device that can be used in the implementation of the present invention; and

FIG. 3 is a schematic representation of the circuitry of the electronic device of FIG. 2.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

The present invention provides an improved system and method for implementing communications hand over in a simple manner. In various embodiments of the present invention, RTP is used to signal other users that an IP address has been changed. The receiving communications application notices from the RTP data flow that the other party in a communications session has changed its IP address. Based on this information, the communications application adjusts the communications session without having to perform any session signaling.

According to various embodiments of the present invention, whenever an IP-based terminal of a user attaches to a new network, where the terminal has the highest priority in the terminal routing table, or whenever the interface with highest priority is detached from the network, the default route in the terminal routing table is changed. In this situation, the communications session is not interrupted during the various embodiments of the present invention. Instead, the communications application continues to send RTP packets to the intended destination with the new source IP address. In these transmission, the same synchronization source (SSRC) identifier is used in the RTP headers as was used previously, and the timestamp and sequence continue without interruption. As the receiving communications application notices that the sender's IP address has been changed in the RTP packets, it adapts to this and also starts sending its RTP packets to the new IP address used by the other party. At the same time, the user whose IP address has been changed is also expecting to receive packets from the new interface. Based on these changes in the RTP flows, both parties modify the session information and/or parameters without making any new signaling. This hand over process does not change anything else in the communications session except the IP address of one of the parties involved. There is therefore no need to perform a session update.

FIG. 1 is a depiction of the process by which a changed interface/IP address is signaled using RTP packets in accordance with one embodiment of the present invention. At 120 in FIG. 1, session startup signaling is conducted between a first terminal 100 and a second terminal 110. At 130, once the session startup signaling is completed, RTP packets are transferred between the terminals in a normal manner. At 140, a new interface is selected for the first terminal. In response to this occurrence, at 150 subsequent RTP packets are sent to the same IP address for the second terminal, with these RTP packets possessing a new source IP address but the same SSRC identifier. Additionally, the packets are transmitted using the ongoing timestamps and sequence numbers.

Upon receiving the RTP packets from the first terminal 100 with the new IP address, at 160 the second terminal 110 updates its settings and transmits new RTP packets to the first terminal 100 at the new IP address. From this point forward, subsequent RTP packets are transferred 170 between the first terminal 100 and the second terminal 110 as normal.

Until the second terminal 110 notices that the IP address for the first terminal 100 has changed, the second terminal continues to send packs to the old IP address of the first terminal. In the event that the first terminal 100 still has the previously-used interface active, then it can continue to receive packets via the old interface from the second terminal 110 until the second terminal adapts to sending to the new IP address. In this case no break will occur in the communications session. In the event that an IP address is changed because of a previous default interface is detached from the network (e.g. a connection is lost), then a break will occur in the communication from the second terminal 100 towards the first terminal 110 until the second terminal 110 has noticed the change and has adapted accordingly.

In implementing the various embodiments of the present invention, few changes are required to existing system requirements. In particular, the Network Working Group's Request for Comments (RFC) 3550, which can be found at www.ietf.org/rfc/rfc3550.txt and is incorporated by reference herein in its entirety, states in chapter 8.2 that “if a source changes its source transport address, it may also choose a new SSRC identifier to avoid being interpreted as a looped source.” Therefore, RFC 3550 permits the same SSRC to be used when the IP address is changed.

The various embodiments of the present invention is suitable for use in IP-based communications in a flat rate type of charging systems. Additionally, the various embodiments can be implemented with regard Internet-model lightweight communications that do not keep tight control of network events.

The system and method of the various embodiments of the present invention is suitable with all different signaling protocols, e.g., Session Initiation Protocol (SIP), H.323, Media Gateway Control Protocol (MGCP), etc. Additionally, no equipment or control is needed in the network to assist in the “hand over” from one interface to another. Instead, the various embodiments can be implemented purely within the terminal applications. Additionally, the terminal can make decisions about which interfaces to use, prefer and prioritize. Furthermore, no additional signaling traffic is required in the communications control layer, and any party to a communications session can perform the hand over. Still further, the various embodiments of the present invention are not tied to any specific access technology. Instead, the various embodiments can be used within the same access in the event that the IP address is changed (e.g. from one WLAN hotspot to another WLAN hotspot), or the embodiments can be used when moving from one access network to another (e.g. from a WCDMA network to a WLAN network). The accesses that are used by a terminal can come from different operators.

FIGS. 2 and 3 show one representative electronic device 12 within which the present invention may be implemented. It should be understood, however, that the present invention is not intended to be limited to one particular type of electronic device 12 or other electronic device. The electronic device 12 of FIGS. 2 and 3 includes a housing 30, a display 32 in the form of a liquid crystal display, a keypad 34, a microphone 36, an ear-piece 38, a battery 40, an infrared port 42, an antenna 44, a smart card 46 in the form of a UICC according to one embodiment of the invention, a card reader 48, radio interface circuitry 52, codec circuitry 54, a controller 56, and a memory 58. Individual circuits and elements are all of a type well known in the art, for example in the Nokia range of mobile telephones.

The exemplary communication devices which are capable of implementing various embodiments of the present invention may include, but are not limited to, a mobile telephone, a combination PDA and mobile telephone, a PDA, an integrated messaging device (IMD), a desktop computer, and a notebook computer. The communication devices may be stationary or mobile as when carried by an individual who is moving. The communication devices may also be located in a mode of transportation including, but not limited to, an automobile, a truck, a taxi, a bus, a boat, an airplane, a bicycle, a motorcycle, etc. The communication devices may communicate using various transmission technologies including, but not limited to, CDMA, GSM, Universal Mobile Telecommunications System (UMTS), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Transmission Control Protocol/Internet Protocol (TCP/IP), Short Messaging Service (SMS), Multimedia Messaging Service (MMS), e-mail, Instant Messaging Service (IMS), Bluetooth, IEEE 802.11, etc. A communication device may communicate using various media including, but not limited to, radio, infrared, laser, cable connection, and the like.

The present invention is described in the general context of method steps, which may be implemented in one embodiment by a program product including computer-executable instructions, such as program code, executed by computers in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

Software and web implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps. It should also be noted that the words “component” and “module,” as used herein and in the claims, is intended to encompass implementations using one or more lines of software code, and/or hardware implementations, and/or equipment for receiving manual inputs.

The foregoing description of embodiments of the present invention have been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the present invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the present invention. The embodiments were chosen and described in order to explain the principles of the present invention and its practical application to enable one skilled in the art to utilize the present invention in various embodiments and with various modifications as are suited to the particular use contemplated. 

1. A method of implementing a hand over in a Real-Time Transport Protocol (RTP) communications session, comprising: receiving through a first interface a first plurality of RTP packets from a remote terminal, the first plurality of RTP packets being directed to an initial IP address and including a synchronization source (SSRC) identifier; initiating a second interface; transmitting a second plurality of RTP packets to the remote terminal, the second plurality of packets including a new IP address and the same SSRC identifier.
 2. The method of claim 1, further comprising, in response to having the transmitted second plurality of RTP packets received by the remote terminal, receiving a third plurality of RTP packets through the second interface from the remote terminal, the third plurality of RTP packets being directed to the new IP address.
 3. The method of claim 1, further comprising: maintaining use of the first interface after the initiation of the second interface; and continuing to receive RTP packets through the first interface at least until the remote terminal has received RTP packets indicating the new IP address.
 4. The method of claim 1, wherein the second plurality of RTP packets are transmitted using timestamps and sequences that continue in order, without interruption, relative to previously-transmitted RTP packets.
 5. A computer program product, embodied in a computer-readable medium, for implementing a hand over in a Real-Time Transport Protocol (RTP) communications session, comprising: computer code for processing a first plurality of RTP packets received through a first interface from a remote terminal, the first plurality of RTP packets being directed to an initial IP address and including a synchronization source (SSRC) identifier; computer code for initiating a second interface; computer code for transmitting a second plurality of RTP packets to the remote terminal, the second plurality of packets including a new IP address and the same SSRC identifier.
 6. The computer program product of claim 5, further comprising computer code for, in response to having the transmitted second plurality of RTP packets received by the remote terminal, processing a third plurality of RTP packets received through the second interface from the remote terminal, the third plurality of RTP packets being directed to the new IP address.
 7. The computer program product of claim 5, further comprising: computer code for maintaining use of the first interface after the initiation of the second interface; and computer code for continuing to process RTP packets received through the first interface at least until the remote terminal has received RTP packets indicating the new IP address.
 8. The computer program product of claim 5, wherein the second plurality of RTP packets are transmitted using timestamps and sequences that continue in order, without interruption, relative to previously-transmitted RTP packets.
 9. An apparatus, comprising: a processor; and a memory unit communicatively connected to the processor and including: computer code for processing a first plurality of RTP packets received through a first interface from a remote terminal, the first plurality of RTP packets being directed to an initial IP address and including a synchronization source (SSRC) identifier; computer code for initiating a second interface; computer code for transmitting a second plurality of RTP packets to the remote terminal, the second plurality of packets including a new IP address and the same SSRC identifier.
 10. The apparatus of claim 9, wherein the memory unit further comprises computer code for, in response to having the transmitted second plurality of RTP packets received by the remote terminal, processing a third plurality of RTP packets received through the second interface from the remote terminal, the third plurality of RTP packets being directed to the new IP address.
 11. The apparatus of claim 9, wherein the memory unit further comprises: computer code for maintaining use of the first interface after the initiation of the second interface; and computer code for continuing to receive RTP packets through the first interface at least until the remote terminal has received RTP packets indicating the new IP address.
 12. The apparatus of claim 9, wherein the second plurality of RTP packets are transmitted using timestamps and sequences that continue in order, without interruption, relative to previously-transmitted RTP packets.
 13. A method of implementing a hand over in a Real-Time Transport Protocol (RTP) communications session, comprising: transmitting a first plurality of RTP packets to a first interface of a remote terminal, the first plurality of RTP packets being directed to an initial IP address and including a synchronization source (SSRC) identifier; receiving a second plurality of RTP packets from the remote terminal, the second plurality of packets including a new IP address for the remote terminal and the same SSRC identifier; and in response to the received second plurality of RTP packets, transmitting a third plurality of RTP packets to the remote terminal through a second interface corresponding to the new IP address.
 14. The method of claim 13, wherein the second plurality of RTP packets include timestamps and sequences that continue in order, without interruption, relative to RTP packets previously transmitted by the remote device.
 15. A computer program product, embodied in a computer-readable medium, for implementing the processes of claim
 13. 16. An apparatus, comprising: a processor; and a memory unit communicatively connected to the processor and including: computer code for transmitting a first plurality of RTP packets to a first interface of a remote terminal, the first plurality of RTP packets being directed to an initial IP address and including a synchronization source (SSRC) identifier; computer code for processing a second plurality of RTP packets received from the remote terminal, the second plurality of packets including a 11 new IP address for the remote terminal and the same SSRC identifier; and computer code for, in response to the received second plurality of RTP packets, transmitting a third plurality of RTP packets to the remote terminal through a second interface corresponding to the new IP address.
 17. The apparatus of claim 16, wherein the second plurality of RTP packets include timestamps and sequences that continue in order, without interruption, relative to RTP packets previously transmitted by the remote device.
 18. A system comprising: a first terminal; and a second terminal configured to: receive through a first interface a first plurality of RTP packets from the first terminal, the first plurality of RTP packets being directed to an initial IP address and including a synchronization source (SSRC) identifier; initiate a second interface; transmit a second plurality of RTP packets to the first terminal, the second plurality of packets including a new IP address for the second terminal and the same SSRC identifier.
 19. The system of claim 18, wherein the first terminal is configured to, in response receiving the second plurality of RTP packets from the second terminal, transmit a third plurality of RTP packets to the second terminal through the second interface corresponding to the new IP address.
 20. The system of claim 18, wherein the second plurality of RTP packets include timestamps and sequences that continue in order, without interruption, relative to RTP packets previously transmitted by the second terminal.
 21. The system of claim 1, wherein the second terminal is configured to: continue the use of the first interface after the initiation of the second interface; continue receiving RTP packets through the first interface from the first terminal at least until the first terminal has received RTP packets indicating the new IP address. 